Skip to content

Add process requirements for AoU linking#599

Open
aschemmel-tech wants to merge 1 commit intomainfrom
aschemmel-tech-fulfil-aou
Open

Add process requirements for AoU linking#599
aschemmel-tech wants to merge 1 commit intomainfrom
aschemmel-tech-fulfil-aou

Conversation

@aschemmel-tech
Copy link
Contributor

Resolves: #597

@github-actions
Copy link

github-actions bot commented Mar 4, 2026

The created documentation from the pull request is available at: docu-html

@aschemmel-tech aschemmel-tech marked this pull request as ready for review March 4, 2026 14:08
@aschemmel-tech
Copy link
Contributor Author

Requested infrastructure team review if the requirements are understood and can be implemented

Comment on lines +268 to +269
It shall be checked that architecture elements are not linked to its own AoU
("own" means the AoU linked as "mitigated_by" to the Safety/Security Analysis linked via "violates" to the element)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you make an example here I don't quiet get what is allowed and what isn't.

Comment on lines +202 to +208
Requirements shall be linked to AoU via the attribute satisfies, if they already satisfy these.

* AoU <- feature requirements
* AoU <- component requirements

Note: "Already" illustrates the understanding that AoU come from used (external) components
which appear later in the development (after deciding an architecture).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't depicted in the picture here
Is this something new?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improvement: AoU linkage

2 participants